Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.20.1
-
None
-
None
-
Incompatible change, Reviewed
Description
When a HighRAMJob turns up at the head of the queue, the current implementation of support for HighRAMJobs in the Capacity Scheduler has problem in that the scheduler stops assigning tasks to all TaskTrackers in the cluster until a HighRAMJob finds a suitable TaskTrackers for all its tasks.
This causes a severe utilization problem since effectively no new tasks are allowed to run until the HighRAMJob (at the head of the queue) gets slots.
Attachments
Attachments
Issue Links
- is blocked by
-
HADOOP-5884 Capacity scheduler should account high memory jobs as using more capacity of the queue
- Resolved
- is related to
-
HADOOP-5881 Simplify configuration related to task-memory-monitoring and memory-based scheduling
- Resolved
-
MAPREDUCE-3789 CapacityTaskScheduler may perform unnecessary reservations in heterogenous tracker environments
- Closed
-
MAPREDUCE-4001 Improve MAPREDUCE-3789's fix logic by looking at job's slot demands instead
- Closed